Product
Socket Now Supports uv.lock Files
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
@unified-latex/unified-latex-types
Advanced tools
Types for the unified-latex
Abstract Syntax Tree (AST). These types extend the unist
AST,
but instead of a children
attribute, they have a content
attribute.
If you're working with unified-latex
ASTs.
npm install @unified-latex/unified-latex-types
This package contains both esm and commonjs exports. To explicitly access the esm export,
import the .js
file. To explicitly access the commonjs export, import the .cjs
file.
ArgumentParser
export type ArgumentParser = (
nodes: Ast.Node[],
startPos: number
) => { args: Ast.Argument[]; nodesRemoved: number };
Ast
export type Ast = Node | Argument | Node[];
EnvInfo
export type EnvInfo = {
renderInfo?: {
/**
* Whether the body of the environment should be treated as math mode
*
* @type {boolean}
*/
inMathMode?: boolean;
/**
* Whether to align the environment contents based on `&` and `\\` delimiters
* (like a matrix or tabular environment).
*
* @type {boolean}
*/
alignContent?: boolean;
/**
* Whether the arguments should be treated as pgfkeys-type arguments.
*
* @type {boolean}
*/
pgfkeysArgs?: boolean;
/**
* A list of names to be given to each argument when processing. This list should
* be the same length as the number of arguments. `null` can appear any number of times
* for "un-named" arguments.
*
* This allows a consistent reference to macro arguments even if the macro signatures are redefined between
* packages.
*
* @type {((string|null)[])}
*/
namedArguments?: (string | null)[];
/**
* Whether the body is tikz-environment like (e.g., a `tikzpicture` or `scope`, etc.)
*
* @type {boolean}
*/
tikzEnvironment?: boolean;
};
/**
* Function to process the body of an environment. The return value of `processContent`
* is treated as the new body.
*
*/
processContent?: (ast: Ast.Node[]) => Ast.Node[];
/**
* The environment signature as an xparse argument specification string.
*
* @type {string}
*/
signature?: string;
};
EnvInfoRecord
export type EnvInfoRecord = Record<string, EnvInfo>;
GenericAst
export type GenericAst = GenericNode | GenericNode[];
MacroInfo
export type MacroInfo = {
renderInfo?: {
/**
* Whether the macro's contents wraps along with the current
* paragraph or displays as it's own block.
*
* @type {boolean}
*/
inParMode?: boolean;
/**
* Whether the arguments should be processed as pgfkeys-type arguments.
*
* @type {boolean}
*/
pgfkeysArgs?: boolean;
/**
* Whether there should be line breaks after the macro
* (e.g., like the `\\` command.)
*
* @type {boolean}
*/
breakAfter?: boolean;
/**
* Whether there should be line breaks before and after the macro
* (e.g., like the `\section{...}` command.)
*
* @type {boolean}
*/
breakAround?: boolean;
/**
* Whether there should be line breaks before the macro.
*
* @type {boolean}
*/
breakBefore?: boolean;
/**
* Whether the contents of the macro should be assumed to be in math mode.
*
* @type {boolean}
*/
inMathMode?: boolean;
/**
* Whether the arguments should be rendered with a hanging indent when the wrap
* (like the arguments to \item in an enumerate environment.)
*
* @type {boolean}
*/
hangingIndent?: boolean;
/**
* A list of names to be given to each argument when processing. This list should
* be the same length as the number of arguments. `null` can appear any number of times
* for "un-named" arguments.
*
* This allows a consistent reference to macro arguments even if the macro signatures are redefined between
* packages.
*
* @type {((string|null)[])}
*/
namedArguments?: (string | null)[];
/**
* Whether the macro represents a tikz path command (e.g. `\draw (0,0) -- (1,1);`).
*
* @type {boolean}
*/
tikzPathCommand?: boolean;
/**
* If `\sysdelims` is present, this contains the global information about the delimiters.
*/
sysdelims?: (Ast.Node[] | null)[];
};
/**
* The macro signature as an xparse argument specification string.
*
* @type {string}
*/
signature?: string;
/**
* Some special macros like `^` and `_` don't use
* an escape token. When matching against these macros,
* care must be taken to match the macro contents and the macro's
* escape token.
*/
escapeToken?: string;
/**
* Custom argument parser. If present, function overrides the default argument
* parsing of `signature`. An array of nodes is passed as well as the position
* of the first node **after** the macro. This function is expected to _mutate_
* the input array, removing any nodes that are part of the macro's argument.
*
* This function will only be called on a macro if it has no existing `args`.
*
* Note: for stability when printing/accessing a node's arguments, this function
* should always return an argument array of the same length, regardless of
* whether optional arguments are present. For example, if this function parses
* a node with signature `o m`, it should ways return a length-two array of arguments.
* A "blank" argument (one that does not show up during printing) can be created
* with `args([], { openMark: "", closeMark: "" })`, using the `unified-latex-builder` package.
*/
argumentParser?: ArgumentParser;
};
MacroInfoRecord
export type MacroInfoRecord = Record<string, MacroInfo>;
Node
export type Node =
| Root
| String
| Whitespace
| Parbreak
| Comment
| Macro
| Environment
| VerbatimEnvironment
| InlineMath
| DisplayMath
| Group
| Verb;
v1.8.0
amsart
macros\o y
produces øy
instead of ø y
\hyphenation
FAQs
type definitions for unified-latex
The npm package @unified-latex/unified-latex-types receives a total of 3,117 weekly downloads. As such, @unified-latex/unified-latex-types popularity was classified as popular.
We found that @unified-latex/unified-latex-types demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.
Security News
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.